[WIP] Reclaim backoff for re-borrowing after preemption-driven reclamation - #14470
[WIP] Reclaim backoff for re-borrowing after preemption-driven reclamation#14470hahahaheihei wants to merge 7 commits into
Conversation
✅ Deploy Preview for kubernetes-sigs-kueue canceled.
|
|
Important Review skippedAuto reviews are limited based on label configuration. 🚫 Excluded labels (none allowed) (3)
Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Hi @hahahaheihei. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Regular contributors should join the org to skip this step. Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: hahahaheihei The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
/ok-to-test |
…e, prune on read path
|
PR needs rebase. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
What type of PR is this?
/kind feature
/kind api-change
What this PR does / why we need it:
Implements the reclaim backoff proposed in KEP-14468 (design review in progress). After a ClusterQueue's borrowed resource is reclaimed by cohort preemption, the scheduler applies an exponentially growing cooldown during which it defers only the flavor assignments that would borrow that same resource again. This breaks the "admitted, then immediately reclaimed again" spin loop without changing quota semantics for well-behaved workloads.
The feature is opt-in via a new
reclaimBackoffblock in the v1beta2 Configuration API and disabled by default./hold
Hold until the KEP is accepted.
Which issue(s) this PR fixes:
Part of #14468
Special notes for your reviewer:
KEP under review: #14469
Submitted as a draft reference implementation to aid the KEP discussion. Verified locally:
make verify, unit tests, the new integration suite (test/integration/singlecluster/scheduler/reclaimbackoff), and the e2e baseline (62/62) all pass.Does this PR introduce a user-facing change?